Priority 1 (the must-do)
The single most important thing this week. If you only accomplish one thing, this is it. Write a specific outcome, not an activity: 'Ship the onboarding modal' not 'Work on onboarding.' Specific outcomes are completable; activities are endless.
Priority 2 (the should-do)
The second most important thing. Closely behind Priority 1 in importance. If Priority 1 is done by Wednesday, Priority 2 is what you move to without needing to decide. Already decided.
Priority 3 (the want-to-do)
The third priority — important, but not at the cost of the first two. If it slips to next week because something urgent came up, that's acceptable. Write it anyway — naming it makes it real and prevents it from falling off the radar entirely.
Dependencies
A small section below the priorities: what does this week depend on that's outside your control? A code review from someone else, a client response, a third-party API. Name the dependency and the contact. If the dependency is blocked, one of your priorities may need to change.
Carry-over from last week
One row at the bottom: what didn't get done last week that still matters? Write it here — either it becomes Priority 2 or 3, or you explicitly decide it doesn't matter and cross it out. Don't let it invisibly haunt the week.