journey-map
Installation
SKILL.md
Journey Map
Core principle: A journey map is a user-centered narrative. It answers "what is this person going through?" not "how does our system work?" — that's the blueprint's job.
Build from Evidence
Read code (routes, controllers, mailers, views) to extract touchpoints and channels. Read transcripts and support tickets to extract thoughts and emotions. Code reveals what the user encounters; it cannot reveal what they think or feel. Accept docs, pasted content, URLs — ingest, don't summarize.
Set Boundaries First
One scenario, one actor. Define start and end from the actor's POV. Three lenses:
| Lens | What it prevents |
|---|---|
| Lifecycle sequencing (pre/during/post) | Optimizing one moment while degrading surroundings |
| Context of use (environment, stakes, frequency) | Designing for a user who doesn't exist |
| JTBD forces (functional, social, emotional) | Reducing the journey to task completion |