Confirm Request

Applicability (check first)

This skill depends entirely on the confirmation flow shipped in sprintify's base code. Check opportunistically:

• If the project ships its own .ai/skills/confirm-request/, defer to that copy.
• Verify both halves exist: src/Support/Http/Confirmation/ConfirmRequest.php (backend) and a confirmRequest interceptor in resources/js/services/http.ts (frontend replay).
• If either is missing (the project forked before this flow existed): skip this skill entirely, tell the user the project predates confirmRequest(), and build the confirmation as an ordinary explicit frontend dialog instead. Don't port the module uninvited.

When to Activate

• An endpoint needs an "are you sure?" confirmation or a password re-check before a destructive or sensitive action (email change, TFA changes, logging out other sessions, deletions with side effects).
• You see $this->confirmRequest(...), ConfirmationHttpException, code: 'confirmation_required', HTTP 428 responses, or X-Confirmation-* headers.

Scope

• In scope: backend usage of confirmRequest(), its HTTP contract, and how to test it.
• Out of scope: generic sprintify-ui dialogs (useDialogsStore), authorization (policies — see the authorization skill).