Task Me Directions¶

How to run /wb-task-me — the re-runnable engage flow that answers what should I do right now

When to use¶

user runs /wb-task-me or asks what to work on right now

Slash command: /wb-task-me

Linked workflow: task-me

Run mcp__work-buddy__wb_run("task-me") and follow the conductor.

The workflow has 4 steps:

load-context (auto_run) — composes:
task_briefing (focused / mit / overdue / inbox / stale buckets)
calendar (today's events; best-effort)
contract_constraints (WIP limits + active contracts)
the Slice-5a engage view (per-task tier x who_can_act x user_now)
build-now-plan (auto_run) — generates a clamp-to-now timeline from focused tasks + calendar. Uses the engage view's filtered set so context-blocked tasks don't land in the plan.
engage (you, reasoning) — present:
Top contract-constraint banner (if any active contracts)
ONE recommendation card with rationale traced to the active contract OR explicitly labeled "exploration"
ONE alternative if a sensible second exists
The plan as a compact list (time block + task)

Keep this brief. V1a — attention scarcity. No more than 2 cards. If everything is blocked on missing contexts, name the contexts and link to /setup.

write-back (you, reasoning, OPTIONAL) — only if the user explicitly asks to write the plan into the journal Day Planner. Calls day_planner_generate_and_write. Skip silently if not asked.

The slash command may be passed an optional preset: - — default; assumes filesystem + vault + web + workstation - -

These map to the user_current_contexts list. If unset, the workflow runs without filtering — every task surfaces with its blocker badge.

Designed to be called multiple times per day. Each run is independent; no state is mutated unless the user opts into write-back.