agentleFS
45ck45ck/hci-review-skill/.agents/skills/journey-map/SKILL.md

journey-map

Skill19 starsChanged 6 days agoMITView on GitHub

Map the key user journeys for a prototype, including happy paths, edge cases, decision points, and recovery flows.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use interview-guide and prioritize.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nbirknerSkill

    interview-guide

    Use when preparing to conduct user research interviews and needing structured JTBD-based questions. Also use when starting a new discovery research effort or when existing interview questions feel generic. Keywords: interview guide, user research questions, discovery interview, JTBD questions, research script.

    Also in 4 projects that use this

  • blueOctopusAISkill

    prioritize

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use ultrathink. Work from the current prototype, routes, components, docs, screenshots, and any existing flows.

    line 11
  2. Very specific:

    Write docs/hci/user-journeys.md unless the user asked for another path.

    line 14
  3. Distinctive:

    Create the directory if it does not exist.

    line 15
  4. Distinctive:

    Add Mermaid flowcharts for the most important journeys.

    line 29
  5. Distinctive:

    Keep the flow specific to the actual prototype.

    line 52

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Map the key user journeys for this scope:

$ARGUMENTS

Use ultrathink. Work from the current prototype, routes, components, docs, screenshots, and any existing flows. Infer missing pieces conservatively.

Output

Write docs/hci/user-journeys.md unless the user asked for another path. Create the directory if it does not exist.

Required process

  1. Identify the 3 to 7 most important journeys.
  2. Prioritize first-time use, core task completion, edit/undo, failure recovery, and returning user behavior.
  3. For each journey, document:
    • goal
    • trigger / entry point
    • steps
    • decision points
    • alternate branches
    • errors and recovery
    • exit state
    • likely confusion points
  4. Add Mermaid flowcharts for the most important journeys.
  5. Summarize cross-journey friction themes.

Output structure

For each journey use:

  • Journey name
  • User goal
  • Preconditions
  • Main flow
  • Alternative flow(s)
  • Error path(s)
  • Exit state
  • Confusion risks
  • Design recommendation(s)

Synthesis

End with:

  • journeys most likely to fail for first-time users
  • shared friction points across multiple journeys
  • dead ends and missing recovery paths
  • design changes with the highest impact on task completion

Quality bar

  • Keep the flow specific to the actual prototype.
  • Focus on what the user must perceive and decide, not just backend events.
  • Flag hidden dependencies, missing feedback, dead ends, and branch explosions.

Deliverable style

  • Clear headings
  • Markdown tables
  • Mermaid diagrams where useful
  • Direct language
  • No filler

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.