Prototype user flows

I need the user flows for onboarding prototyped so engineers and PMs can test handoffs. Start with the signup path for returning users who skipped verification, include the email-resent screen, the verification success state, and the first-time dashboard tour. Link screens so the 'resend email' and 'skip tour' actions navigate correctly. Finish by flagging any missing microcopy or assets. Deadline Friday EOD.

Before I hand this onboarding prototype to product for usability testing, make the key decisions visible: surface the conversion funnel (signup → verify → first task) on the first frame, highlight the points where users can drop off, make the primary CTAs consistent across screens, and call out any broken or placeholder flows that would confuse testers.

We just ran a quick usability run and three users hit the resend email flow and then abandoned. I need a diagnosis and the next move. Tell me the likely reason they quit (copy, timing, perceived spam risk, or flow loop) and the single best change to prototype and retest tomorrow morning.

Over the last three launches we keep redoing onboarding screens after engineering sprints start. Where is the time lost and what single habit should I change so prototypes ship with fewer surprises? Be concrete: what checklist, naming convention, or stage gate to add before handoff.