Problem and audience

☐ One primary audience is named.
☐ The painful job is stated in plain language.
☐ You know the current workaround.
☐ The MVP has one learning goal.

Core product path

☐ A new user can reach the promised outcome.
☐ Required data saves and reloads correctly.
☐ Empty, error and loading states are understandable.
☐ The critical flow works on mobile.

Accounts and permissions

☐ Sign-up, sign-in and sign-out work if accounts are required.
☐ Password recovery has been tested.
☐ Users cannot see another user's private records.
☐ Admin-only actions are actually protected.

Commercial basics

☐ Pricing is understandable.
☐ Test payments complete correctly if you charge at launch.
☐ Successful payment grants the right access.
☐ Cancellation/refund handling is defined.

Launch readiness

☐ A real production URL has been tested.
☐ Secrets are not exposed in front-end code.
☐ The primary workflow has been tested in a private browser session.
☐ There is a support/contact route.
☐ You know which behaviour will count as activation.

After launch

☐ Collect recurring questions and failures.
☐ Fix the core path before adding peripheral features.
☐ Add a feature when evidence supports it, not merely because it is easy to generate.