Journey and Performance Evidence

VibePro can make user journeys and performance evidence part of the same PR readiness model as tests and reviews.

Journey map

Generate a journey map from Story metadata:

vibepro journey derive .
vibepro journey status .
vibepro journey map .

The journey map helps reviewers answer:

• Which product path does this Story affect?
• Is the walking skeleton covered?
• Are multiple Stories fighting over the same transition?
• Which open questions remain before release?

When a PR affects a path, connect it to flow verification:

vibepro verify flow . --base-url http://localhost:3000 --id <story-id> --journey <journey-id>

Performance evidence

For broad local measurement:

vibepro measure . --base-url http://localhost:3000 --pages /,/settings --samples 5
vibepro measure compare . --before before-performance.json --after after-performance.json

For Story-specific performance acceptance:

vibepro performance define . \
  --id <story-id> \
  --metric-id page-ready \
  --user-story "User opens the dashboard" \
  --start-condition "navigation starts" \
  --completion-condition "dashboard is interactive"

vibepro performance record . --id <story-id> --metric-id page-ready --label after --status completed --duration-ms 1200
vibepro performance compare . --id <story-id> --metric-id page-ready

Use performance evidence when speed is part of the user promise, not as an afterthought once the PR is ready.