Journey Storymapping

Shaping and diagnosing product experiences with narrative structure — casting the user as the protagonist and mapping how their experience unfolds as a story arc. Provenance and grounding sources live in skill.json; this file is runtime routing only.

Produces: a story map (arc with beats) or a concept/origin story; the diagnose-experience intent returns the broken-beat diagnosis inline.

Core principle

The user is the protagonist; the product is the helper. A good experience reads like a story — a character with a goal, an event that sets them in motion, rising stakes, and a satisfying climax near the end. Mapping an experience onto that arc shows how it feels to move through it and exactly where it stalls. Use story where the experience genuinely has an arc; a habitual or nonlinear flow may not, and forcing one onto it misleads.

Activation