user-journeyslisted

# User Journeys Skill For defining and testing real user experiences - not just specs, but actual flows humans take through your application. --- ## Philosophy **Specs test features. Journeys test experiences.** A feature can pass all specs but still deliver a terrible experience. User journeys capture: - How users actually navigate (not how we think they should) - Emotional states at each step (frustrated, confused, delighted) - Recovery from mistakes (users will make them) - Real-world conditions (slow networks, interruptions, distractions) --- ## Journey Documentation Structure ``` _project_specs/ ├── journeys/ │ ├── _template.md # Journey template │ ├── critical/ # Must-work journeys (revenue, core value) │ │ ├── signup-to-first-value.md │ │ ├── checkout-purchase.md │ │ └── login-to-dashboard.md │ ├── common/ # Frequent user paths │ │ ├── browse-and-search.md │ │ ├── update-profile.md │ │ └── invite-team-member.md │ └── edge-cases/ # Error recovery, unusual paths │ ├── payment-failure-retry.md │ ├── session-timeout-recovery.md │ └── offline-reconnection.md ``` --- ## Journey Template ```markdown # Journey: [Name] ## Overview | Attribute | Value | |-----------|-------| | **Priority** | Critical / High / Medium | | **User Type** | New / Returning / Admin | | **Frequency** | Daily / Weekly / One-time | | **Success Metric** | Conversion rate, time to com