my_day daily work queue: one authoritative queue—not twelve morning tabs
8:45 AM. Email, Slack, notifications, calendar invites, "quick questions"—before the first commit, it is unclear what to work on. The PM says "know your priorities"—but priorities sprawl across three systems.
The daily work queue via WKFGo's MCP tool my_day compresses that chaos: one query from live assignments, due dates, pending approvals, and blockers—sorted for today. AI in Cursor, Claude Desktop, or the in-app chatbot explains the list; you enter execution intentionally with start_work.
This is not another todo app. It is the same PostgreSQL data as /my-tasks—permission-scoped, current, and connected to time tracking and approvals.
Symptoms and cost of morning tab sprawl
| Symptom | Cost |
|---|---|
| Check email before the board | Reactive day; deep work never starts |
| Same overdue items every morning | Blockers hidden or unowned |
| Standup rebuilds priorities orally | Meeting time instead of execution |
| Context-switch every twenty minutes | Fragmented log_time and progress |
| "Quick question" becomes two hours | Queue authority lost to Slack |
The hidden cost is not one distracted morning—it is a team that never reaches flow because nobody agreed what "today" means before the first ping arrived.
my_day vs my_queue vs dashboard
| Tool | Use |
|---|---|
my_day |
Today's focus—daily planning |
my_queue |
Broader assigned backlog beyond today |
/my-tasks |
Full UI list with filters |
/dashboard |
Team Kanban—not personal queue |
my_day is a subset of my_queue. If today looks light, pull the next item from my_queue intentionally—prevent a false "done" feeling when backlog still exists.
Six-step morning ritual framework
Step 1: Pull my_day (2 minutes)
MCP: "Call my_day and list my top five."
Chatbot: "What should I work on today?"
Both read live assignments from the backend—not yesterday's memory.
Step 2: Triage (5 minutes)
For each item: blocker? Comment on the card or escalate. Approval stuck? Ping via /task-approvals. Unrealistic for today? Negotiate on the task with PM—do not silently defer.
Step 3: Pick one start (1 minute)
start_work on the primary task—begin session tracking. One active focus beats start_work on five cards.
Step 4: Communicate async (5 minutes)
One team message: "Today: AUTH-442, DOC-18—no blockers." Standup material without a meeting. Pair with squad-wide async dailies to cut status meetings to exceptions only.
Step 5: Protect deep work
Bookmark my_day output—when distracted, return to the queue instead of scrolling Slack. After lunch, run my_day again; call update_progress before context switching.
Step 6: Close the day with end_work
end_work at day end—tomorrow's my_day stays accurate. Managers use weekly workload_heatmap, not daily my_day on every IC—trust async posts plus exception scans.
Anti-patterns
my_dayonly on Mondays—it is a daily habit, not weekly planning theater.- Ignoring the list for Slack reactivity—the queue is authoritative when the board is maintained.
start_workon five tasks at once—one active session; finish or pause explicitly.my_daywithout board updates—stale queue mirrors bad data upstream.- Managers micromanaging daily queues instead of weekly capacity signals.
WKFGo execution stack
my_day— daily prioritized queuemy_queue— wider assigned set when today is lightstart_work/end_work— session trackinglog_time,update_progress— closure and accuracyget_context_pack— context before deep taskslist_pending_approvals— unblock approval bottleneckssubmit_for_review,mark_done— finish lines- Chatbot —
my_day-style questions without MCP config /my-tasks,/task-approvals— browser equivalents
All from live PostgreSQL—the same backend as Kanban on /dashboard.
my_day for different roles
Developer: Morning my_day → get_context_pack on top item → start_work. Deep work block 9–11.
PM: Personal my_day plus list_pending_approvals plus exception scan on /dashboard. Afternoons for stakeholder sync.
Designer: my_day plus search_docs for spec-linked tasks before opening design tools.
Manager: Shorter personal my_day—redirect to decision_inbox and workload_heatmap for team capacity, not individual task lists.
PTO and handoff without "what did I miss" meetings
Before vacation: post my_day summary and reassign open items in /my-tasks. On return: refresh my_day—the queue shows what moved while you were out. No oral catch-up meeting required if the board stayed current.
FAQ — my_day daily work queue
Does it replace PM prioritization?
No—PMs set priority on cards; my_day surfaces it for you each morning.
Remote and async teams?
Ideal—written dailies from my_day replace oral standups when the whole squad participates.
Mobile access?
Web /my-tasks plus chatbot for quick queries; MCP is desktop-first for IDE workflows.
Non-English output?
Prompt in Persian; mixed FA/EN task titles are fine. WKFGo supports bilingual UI and Jalali calendar utilities.
Next step
Tomorrow morning, pull my_day before opening email. Pick one start_work. Post one async daily. Repeat for five days—then shorten standup to exceptions only.
Measuring progress without fake benchmarks
Track observable behaviour over four to six weeks: percentage of assigned tasks touched weekly, status meeting duration, blocker age on cards, and decisions logged in wiki or decision_inbox. If metrics stall after tooling changes, fix board hygiene and permission policy before adding more software.
Permission discipline across UI, chatbot, and MCP
WKFGo resolves identity through JWT or personal wk_ keys and applies FeatureAccess on every tool call. Test with a contractor account before org-wide rollout. Forbidden responses mean permissions work—do not bypass with shared admin tokens.