Personas & jobs-to-be-done

Each journey is walked by a named protagonist (BMAD pattern): a concrete persona with a job-to-be-done trigger, so the spec reads as behaviour rather than abstract requirements.

{{N_PERSONAS}} personas{{N_SCENARIOS}} scenariosslug {{SLUG}} {{PERSONAS}}

Scenario catalog

Every distinct leaf path, classified happy / edge / failure / recovery. The proposed test-IDs are the bridge that plan-techspec reads from scenario_map.json to seed acceptance checks.

ID	Scenario	Persona	Path	Steps	Proposed test-IDs

Scenarios — click-by-click step tables

Each row is one concrete UI interaction: who acts · the exact element clicked or seen · the copy shown · the system action · the resulting state · where it branches.

Global branching flowchart

Conditions on the arrows; colours follow the path-type legend. Per-scenario sub-flows appear inside each scenario above.

Copy index — message · copy · source · mode · status

State reference

Generated by the user-journeys skill on {{GENERATED}} · hosted at {{JOURNEYS_URL}}. Rendering: Mermaid flowchart syntax. No screenshots — this is a behavioral spec, not a visual QA artifact.