Open-Golf: unofficial illustration, not affiliated with its author, MIT, art credits in notices. Click the image for full size.
A skill for coding agents. It turns your app’s screens and user stories into one clickable map with real screenshots, a report and a one-page overview. For iOS, Android and web apps.
A user story map lists what users want to do and shows the screens that support it.
Your coding agent reads the app’s code, takes screenshots and sorts the screens by topic. It marks each story as built, partly built, missing or unverified, and lists the gaps it found. It uses free tools only.
Most teams can’t say quickly which screens their app has, which stories are really built, and where the gaps are. The agent keeps that picture current as the app changes, so you open one page and see it.
The clickable maps work on phones too.
Files for each example: examples/open-golf/ and examples/wikipedia-ios/.
Wikipedia iOS: unofficial illustration, not affiliated with the Wikimedia Foundation, MIT (notices). Click the image for full size.
Get a copy of this repo (git clone https://github.com/enjojoy/user-story-maps) and point your coding agent at it. Then ask in plain words, for example:
Make a story map for my app.
The agent reads the skill, looks through your code, takes screenshots, and writes the map into docs/story-map/. It also adds a short note to your AGENTS.md (or CLAUDE.md) so that later changes keep the map current. The agent’s instructions are in skills/user-story-maps/SKILL.md; you don’t need to read them.
You need Python 3.8 or newer. Pillow is optional but recommended, because the images need it.
Your screenshots and stories are not uploaded. The only network request is an optional font download from Google Fonts, which is off by default.
Screenshots and stories end up in your repo, so use a demo account and fake data. If the app isn’t yours, the map says so and you should check the screenshot licence first.
MIT, see LICENSE. Example screenshots show third-party content under its own terms.