user-journeys

/architect:user-journeys

Trigger

/architect:user-journeys

Purpose

Map the complete user experience from discovery through retention. Produces detailed journey maps that reveal design opportunities, potential drop-off points, and emotional dynamics — directly informing UI/UX decisions, onboarding flows, and feature prioritization.

Workflow

Step 1: Gather Context

Read in this order:

1. architecture-output/_state.json — read first if it exists; use project, personas, mvp_scope, market_research directly — these replace reading intent.json and full markdown files
2. intent.json — only if _state.json.project is absent; extract name, vision, core features
3. SDL — only if _state.json.components is absent; check solution.sdl.yaml first; if absent, read sdl/README.md then the relevant module files. Grep for product: block (screens, coreFlows) and components: block only — do NOT read the full file
4. architecture-output/user-personas.md — only if _state.json.personas is absent; if reading, Grep for persona goals and "Current workflow" sections only
5. architecture-output/mvp-scope.md — only if _state.json.mvp_scope is absent; if reading, Grep for "Must Have" section only
6. architecture-output/deep-research.md — only if _state.json.market_research is absent; if reading, Grep for competitor weakness/UX gaps only

Step 2: Identify Core Journeys

Define 4-6 journeys covering the full lifecycle:

1. Discovery → Signup — how each persona finds and evaluates the product
2. Onboarding → First Value — from signup to the "aha moment"
3. Core Loop — the primary repeated action that delivers ongoing value
4. [Feature-Specific Journey] — for 1-2 key features from MVP scope
5. Error/Recovery — what happens when things go wrong
6. Upgrade/Expansion — from free to paid, or from basic to advanced usage

Step 3: Generate Each Journey Map

For EACH journey, produce ALL of the following: