Create and assign tasks

We need tasks for the sprint kickoff assigned today. Create three tasks: finish the API spec (assignee: Samir, due Wednesday), update the pricing page (assignee: Elena, due next Tuesday), and validate analytics events (assignee: Marco, due Friday). Add the PR link to each task, set priority as high, and notify the assignees in chat.

Before I assign these tasks to the team, make them painless to pick up. Put the acceptance criteria at the top of each card, link the exact files or PRs they need, estimate hours for each task, and call out any dependency that would block completion so someone can deconflict before work starts.

I assigned three sprint tasks and Samir and Elena replied that the scopes are vague and they won't start until acceptance criteria are clear. I can't expand every ticket now. Which one detail should I add first that will unblock most engineers, and what exact sentence should I paste into the task to remove ambiguity?

Every sprint we lose two days because engineers reopen tickets asking for acceptance criteria, and that kills velocity. I want one change to stop this. Which ritual or single field on every task should become mandatory and who should enforce it so tickets are ready before assignment?