What problem does it solve? Teams often confuse user journeys with use cases, UX journey maps, domain rules, or UI flows, producing documents that mix unrelated concerns. This Skill judges whether a request is truly a User Journey and structures one primary user's path from a starting state to an observable completion through multiple meaningful scenes. ## Core Features & Use Cases - Journey Boundary Judgment: Decides whether a request is a User Journey or should be routed to a use case, UX journey map, domain rule, or data model, based on the reader's question rather than format. - Scene and State Mapping: Builds a journey map with user, goal, start point, end point, completion criteria, scenes with observable responses, and explicit state handoffs between scenes. - Branches and Resumption: Documents branches, interruptions, resumptions, and role handoffs, including what state must persist and whether the path returns to the original goal. - Use Case: Given existing screen drafts and a separate journey document, map how a first-time visitor compares products, purchases, and confirms receipt as one coherent user journey, flagging unresolved connections as open questions. ## Quick Start Judge whether this request is a User Journey and map the scenes from the user's starting state to an observable completion, separating out anything that belongs to use cases or domain rules.
