Flows workflow logoFlows
Test Every User Path
0/5 steps0%

Step 1 of 5

Map every user path

You test what you have mapped - build the complete path inventory.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule
Map every user path in this app. Produce a table organized by persona/state (new visitor, logged-out, new user, returning user, admin if exists): each path as a numbered sequence of actions (e.g. 'land on home -> search X -> open result -> start action -> complete'). Include: all happy paths, alternate paths (back buttons, cancels, edits), and error paths (invalid input, missing data, unauthorized access). Number every path for tracking.
Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A numbered inventory of happy, alternate, and error paths per persona.

Should NOT happen

  • An existing feature broke
  • A button only logs to console
  • Data disappears after refresh
  • Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Track what changed, failed, or needs follow-up. Notes export with the flow.

Made with Emergent