A screenshot in,user stories out
“Build something like this” comes with a screenshot, not a backlog. Khint captures the screen, lets you interrogate it with a vision chat, and turns it into well-formed user stories (role, goal, benefit) from one keyboard shortcut, without retyping a single feature.
The backlog is hiding in the picture,
someone has to write it out
A competitor's screen carries a whole feature's worth of stories (every toggle, every state, every flow), but none of it is text you can groom. Staring at the screenshot and typing “As a user I want…” over and over is the chore that eats an afternoon and still misses the empty state nobody clicked into. Khint closes that gap: Capture reads the image and lets you break it down, an Agent you tune once turns each capability into a story, Memory keeps every screen of the feature consistent, and when the backlog is ready the integrations file it without leaving the page.
A screen, turned into a backlog
One captured settings screen, before and after.
- Per-channel toggles: Email · Push · SMS
- Mute all (with a duration picker)
- Digest: daily / weekly radio
- “Quiet hours” time range
- Empty state: “No notifications yet”
- As a user, I want to toggle each channel per type, so I only get alerts where I'll see them.
- As a user, I want to mute everything for a set time, so I'm not pinged during focus blocks.
- As a user, I want a daily or weekly digest, so I can batch low-priority updates.
- As a user, I want quiet hours, so nothing reaches me overnight.
Illustrative: your stories follow whatever story style you wrote into the Action prompt.
One screen, start to a backlog
A “build something like this” screenshot, step by step.
Start a session for the thing you're scoping
Open Memory and start a session: “Notifications revamp”. Every capture and Action you run is logged and Khint keeps a compact running summary, so as you mine screen after screen the model holds the whole feature in context and your stories stay consistent with each other. How Memory works →
Capture the screen you were told to copy
A stakeholder drops a competitor's notification settings screen in Slack and says “we need something like this.” Open the palette (Cmd+Shift+K), pick Capture & ask, and drag a box around it. The image lands pinned in a chat window. Emailed PNG or a phone photo of a whiteboard? Drop it into the Capture tab instead of dragging a box.
Break the screen into capabilities
Ask the vision chat in plain language: “List the distinct things a user can do on this screen, each as its own line.” The screenshot stays in context, so you keep going (“What can they toggle per channel?”, “What's the empty state?”) until the screen is inventoried into the separate slices that should each become a story, no re-uploading between questions.
Shape the inventory into user stories
Save a User stories Agentonce: “rewrite each line as a user story in the form ‘As a [role], I want [goal], so that [benefit]’, and add a one-line note on what's ambiguous.” Select the inventory, hit Cmd+Shift+K, run it: a thin list of features becomes a backlog of well-formed stories pasted right where your cursor is. Don't want to write the prompt? Hit Generate to draft it from a one-line description.
File the stories where the team grooms them
With Jira or Linear connected, the palette grows write rows: a Create issue step drafts each story as a ticket, and hands the key back to paste into the thread. Or chain it: a workflow can inventory, write the stories, then file a Jira or Linear issue in one run. Every screen and story is in your Memory session too, so the backlog reads back as a record of which screens you mined. How integrations work →
Stories are the start, not the end
The drafted stories are reusable text: select one and run a follow-up Action that writes its acceptance criteria, or chain the whole thing: a workflow of up to five steps in series: an Agent that inventories the screen, a second that writes the stories, then a create-issue step that files them. And because Khint ships an MCP server, Claude Desktop or Codex can read the scoping session directly (the screens you captured, the stories you drafted, the tickets you filed) without copy-paste.
Common questions
How is this different from extracting requirements from a screen?
Same capture gesture, different artifact at the end. Requirements come out as system-shall statements describing what the software must do; user stories come out in the role-goal-benefit shape your team grooms and estimates: "As a [role], I want [goal], so that [benefit]". Khint doesn't hardcode either one: the shape is whatever your saved Action's prompt asks for. Write the prompt to emit a numbered list of user stories and that's what every screen gives you back.
Can it draft more than one story from a single screen?
Yes, that's the point of using the vision chat first. A real screen is usually several stories: a list view, a filter, an empty state, a create flow. Pick Capture & ask from the palette, drag a box around the screen, and ask the model to break it into the distinct capabilities a user gets from it. Then run your user-story Action on that inventory so each capability becomes its own story, instead of one giant ticket nobody can estimate.
What if the screenshot was shared in Slack or emailed to me?
Drop the file into the Capture tab. PNG, JPG, WebP, HEIC, GIF, BMP, and TIFF go through the same flow as a live region capture, so a competitor screen a stakeholder pasted into Slack, a designer's exported mockup, or a phone photo of a whiteboard all work the same way. You get the same text out, ready for your story Action.
Where does the screenshot and my text go?
Captures go to the vision model so it can read the image; Actions send only the text you selected, plus, if a Memory session is active, the compacted session summary. Memory sessions live in a local SQLite database on your Mac or PC and are never synced to Khint's servers. Khint's free tier covers 10 AI actions and 5 captures per day with no credit card; paid plans start at €7/mo, with Pro at €29/mo for 100 AI actions a day; every plan includes all the work integrations.
Try it on the next screenshot you're handed
Free with 10 AI actions and 5 captures per day. No credit card. Capture the screen, ask the vision chat, keep the stories.