kandev-escalation

# Escalating to a Human Use this pattern when you cannot proceed without human input: a design decision, missing credentials, ambiguous requirements, or access you do not have. ## When to escalate Escalate when ALL of the following are true: 1. You cannot make the decision yourself based on available context. 2. The decision is required to complete your task. 3. You have already checked comments and memory for prior guidance. Do NOT escalate for routine technical choices you can make independently. ## Escalation procedure ### Step 1: Create the human task Create a new task with a clear question as the title. Leave it unassigned (or assign to `$KANDEV_HUMAN_USER_ID` if that variable is set in your environment). ```bash HUMAN_TASK=$( $KANDEV_CLI kandev task create \ --title "Decision needed: <your specific question here>" \ --description "Context: <1-2 sentences of background> Question: <the specific decision the human needs to make> Options considered: - Option A: <brief description> - Option B: <brief description> Blocked task: $KANDEV_TASK_ID" \ 2>/dev/null ) HUMAN_TASK_ID=$(echo "$HUMAN_TASK" | jq -r '.task_id') ``` ### Step 2: Cross-reference from the blocked task ```bash $KANDEV_CLI kandev tasks message --id "$KANDEV_TASK_ID" \ --prompt "Escalated to human task $HUMAN_TASK_ID. Waiting for decision on: <question>" ``` The Office CLI does not currently expose a secure operation for adding a blocker relationship. The human task description links...