take-task

Take Task

Claim a tracker task and prepare the working environment.

IMPORTANT: If the spec below invokes any deferred tool (e.g. AskUserQuestion), you MUST load and call it as specified. Never skip the call, never substitute a default answer of your own — the tool invocation is part of the contract. This is critical.

Why This Exists

Multiple flows need "claim task + prepare branch": /lets:start, mid-session task switch, direct "візьми таск X". Centralizing ensures consistent branch naming, worktree handling, and session ref saving.

Flow

Step 1: Resolve Task

show task=<task-id>

Verify task exists. Then claim it (set-status is a state change - HARD-FAIL loud if the binding can't run; do NOT proceed to branch setup on a failed claim):

set-status task=<task-id> status=in_progress

Step 2: Check Uncommitted Changes

Before switching branches, check for uncommitted changes:

git status --short

If changes exist and branch switch is needed, ask user:

AskUserQuestion(
  questions=[{
    question: "Uncommitted changes on current branch. What to do?",
    header: "Uncommitted",
    options: [
      { label: "Stash", description: "git stash, switch branch, remind to pop later" },
      { label: "Commit first", description: "Commit changes, then switch branch" },
      { label: "Stay", description: "Skip branch switch - work on current branch" }
    ],
    multiSelect: false
  }]
)

Handle response:

• Stash -> git stash, proceed with branch switch, remind to git stash pop later
• Commit first -> delegate to commit skill, then proceed with branch switch
• Stay -> skip branch switch, warn about mixed work, then continue to Step 5 (the task was already claimed in Step 1 - save its .task state file for the current branch; do NOT stop before it, or detect-task//lets:done are left with a claim but no boundary file).

If staying on current branch (worktree, already correct) or no changes - skip this step.