agentleFS
lalulalilalulali/vespyr/.agents/skills/journey-map/SKILL.md

journey-map

Skill11 starsChanged 11 days agoMITView on GitHub

Visualize user touchpoints, emotional state transitions, and friction points across current workflows. Use when the user says "map the user journey", "where are users getting stuck", "show me the end-to-end experience", or invokes /journey-map before redesigning a flow.

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

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

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 1

    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:

    Before redesigning a flow

    line 22
  2. Very specific:

    Run this before the complete call below, so a non-conformant canvas is never recorded as delivered.

    line 108

“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

Journey Map

What this skill does

Maps the current-state user journey with touchpoints, emotions, and friction. Outputs to artifacts/output/02-research/journey-map.md.

Persona delegation

This skill delegates to @user-researcher. The researcher maps the journey from user data. The skill provides the map structure; @user-researcher provides the journey analysis.

When to use

  • "Map the user's journey for {workflow}"
  • "Where are users getting stuck?"
  • "Show me the end-to-end experience"
  • Before redesigning a flow

Workflow

Step 1: Define the journey scope

Identify the start and end of the journey. Example: "From discovering the product to completing first purchase."

Step 2: Map stages

Walk through each stage of the journey:

  1. Awareness — How do they discover the need/solution?
  2. Consideration — How do they evaluate options?
  3. Decision/Action — What triggers them to act?
  4. Onboarding/First Use — What's the first experience?
  5. Ongoing Use — What's the recurring experience?
  6. Exit/Churn — When and why do they leave?

Step 3: At each stage, capture

  • Touchpoint: Where does the interaction happen? (app, email, support, word of mouth)
  • Action: What does the user do?
  • Emotion: High/Med/Low — with brief description
  • Friction: What makes this stage harder than it should be?
  • Opportunity: What would improve this stage?

Step 4: Output

Write artifacts/output/02-research/journey-map.md:

# Journey Map — {journey name}
**Date:** YYYY-MM-DD
**Evidence basis:** {interviewed N / observed / analytics / support-tickets / survey / hypothesis — pick one, and label unvalidated content in the body}
**User segment:** {who}
**Scope:** {start} → {end}

## Journey Stages
| Stage | Touchpoint | Action | Emotion | Friction | Opportunity |
|-------|-----------|--------|---------|----------|-------------|
| 1. Awareness | {where} | {what} | 😃/😐/😟 {why} | {pain} | {fix} |

## Emotional Arc
| Stage | Emotion | Intensity (1-5) | Driver |
|-------|---------|------------------|--------|
| Awareness | 😃/😐/😟 | {n} | {why} |
| Consideration | 😃/😐/😟 | {n} | {why} |
| Decision | 😃/😐/😟 | {n} | {why} |
| Onboarding | 😃/😐/😟 | {n} | {why} |
| Ongoing use | 😃/😐/😟 | {n} | {why} |
| Exit | 😃/😐/😟 | {n} | {why} |

**Arc summary:** {one line — where it peaks, where it bottoms out, and the single stage that flips it}

## Key Friction Points
1. **{stage}:** {friction} — Impact: {High/Med/Low}

## Priority Opportunities
1. **{stage}:** {opportunity} — Effort: {High/Med/Low}, Impact: {High/Med/Low}

Done when — checked mechanically

These canvases shipped for the whole life of this repo with no gate at all: the template in the Output step could be written to disk verbatim and nothing would notice. discovery_canvas_check.js now checks form and evidence declaration:

node .agents/scripts/discovery_canvas_check.js check --kind journey-map --file artifacts/output/02-research/journey-map.md --json

It requires:

  • no unfilled template placeholders — {direct quotes} and {pain point} are the template, not an artifact
  • **Evidence basis:** declared — one of interviewed / observed / analytics / support-tickets / survey / hypothesis. A canvas that does not say where it came from cannot be read as research, and nothing downstream can tell your finding from your guess
  • when the basis is hypothesis, the body must say so too — announced only in a header, a hypothesis reads as a finding three paragraphs later
  • the kind's structural minimum, below

A green result is not a research finding. The gate checks form and one declaration. It cannot tell you whether the analysis is correct, and it does not pretend to.

Exit 0 conformant · 1 failures · 2 usage/IO error, fail-closed, never a silent pass.

Run this before the complete call below, so a non-conformant canvas is never recorded as delivered. Journey-map minimums: at least 3 stages, because a short map hides the middle where friction actually lives; every stage cell carrying real content (an emoji alone is padding, and padding reads as coverage); an Emotional Arc with a summary sentence; and named Key Friction Points.

State machine integration

At start: Run node .agents/scripts/orchestrator_state.js status At end: Run node .agents/scripts/orchestrator_state.js complete --agent user-researcher --artifact 02-research/journey-map.md

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.