Stats
Actions
Tags
From batondeck
Work the BatonDeck board — claim the next task, do it with full context, complete or hand off, repeat.
How this command is triggered — by the user, by Claude, or both
Slash command
/batondeck:workThe summary Claude sees in its command listing — used to decide when to auto-load this command
Use the batondeck-worker skill. Run the worker loop against the connected BatonDeck MCP server: prefer `wait_for_task` long-polling to pick up work the moment it becomes READY, `claim_task` it, load `get_task_context`, do the work, heartbeat the lease while working, then `complete_task` (or `block_task` / `handoff_task` with a memory note). Repeat until the board is drained or I stop you. $ARGUMENTS
Use the batondeck-worker skill. Run the worker loop against the connected BatonDeck MCP server:
prefer wait_for_task long-polling to pick up work the moment it becomes READY, claim_task it,
load get_task_context, do the work, heartbeat the lease while working, then complete_task
(or block_task / handoff_task with a memory note). Repeat until the board is drained or I stop you.
$ARGUMENTS
npx claudepluginhub tech-sumit/batondeck-plugin --plugin batondeck/workExecutes a development plan end-to-end with checks for <fn-N or idea>. Supports --branch (current|new|worktree) and --review (rp|export|none) options.
/workAuto-classifies tasks from descriptions, folder paths, or issue IDs and routes to workflow orchestrators; resumes existing tasks from .maister folders.
/workAuto-classifies tasks from descriptions, folder paths, or issue identifiers (GitHub/Jira/Azure DevOps) and routes to workflow orchestrators. Resumes existing tasks.
/workExecutes a work plan from a plan/spec/todo file path: clarifies requirements, sets up git branch or worktree, generates prioritized todos, and completes tasks maintaining quality.
/workExecutes epic tasks from blueprint using fresh Claude instances via relay script, with quality gate verification and configurable retries.
/workSets up a workspace for a GitHub open-source issue by forking/cloning the repo, creating a branch, and starting a guided session to fix, review, or propose changes.