Exact Terms

Handoff guide

Statechart vocabulary for multi-step forms.

Use this when a form or builder has back/next movement, validation, async saves, failed steps, and resume behavior.

Copy/paste handoff

Handoff

Before writing code, model this multi-step form as a statechart. Return every state, event, transition table row, guard condition, invariant, rejected transition, side effect, draft persistence rule, recovery path, and acceptance test for refresh, back/next, failed save, retry, two tabs, and resume.

Terms this handoff forces into the work

Statechart

Makes the flow explicit before UI fixes begin.

Invariant

Names facts that must stay true across every transition.

Recovery path

Defines how users continue after partial failure.

Related guides

Common questions

When should I use this template?

Use it for wizards, builders, onboarding flows, checkout flows, setup flows, and any form where state can become inconsistent.

What should happen before implementation?

The agent should return the state model, transition table, failure plan, and acceptance tests before changing component code.