1.14Step 8 — Write `docs/specs/ui-journeys.md`

This file defines where early UI automation should go. Talk to your product owner/product manager. Capture everything they respond to the question "Which pieces of functionality, if broken, would stop the release to Prod?" and put it under "Regression Journeys" section.

Recommended structure

# UI Journeys

## Smoke Journeys
- login
- open primary landing page
- complete business-critical short flow

## Regression Journeys
- account/settings behavior
- create/edit/delete flows
- validation scenarios
- permission boundaries

## Accessibility Targets
- forms
- modals
- key landing pages
- critical transaction flows

## Priority Notes
Explain which journeys matter most and why.

Writing guidance

Use product language, not generic language.

Bad:

• “dashboard stuff”
• “main flow”

Better:

• “Customer checkout with saved address”
• “Admin creates a new coupon”
• “Support user searches for an order and opens details”