task-loop-verify

Task Loop Verification

Verify the current task in the loop and output a completion marker if successful. This skill wraps task-verifier and outputs the marker that the stop hook looks for.

When to Use

Use this skill when:

• You've finished implementing a task and want to verify it
• The stop hook has triggered another loop iteration
• You want to exit the task loop cleanly

Process

Step 1: Read Loop State

First, check for the pointer file and get the state path:

if [[ -f .shipspec/active-loop.local.json ]]; then
  LOOP_TYPE=$(jq -r '.loop_type // empty' .shipspec/active-loop.local.json)
  if [[ "$LOOP_TYPE" == "task-loop" ]]; then
    jq -r '.state_path // empty' .shipspec/active-loop.local.json
  else
    echo "WRONG_LOOP_TYPE"
  fi
else
  echo "NO_POINTER"
fi

If NO_POINTER or WRONG_LOOP_TYPE:

"No active task loop. Run /implement-task <feature> <task-id> to start a task." Stop here.

If state_path found: Check the state file exists:

test -f [state_path] && echo "EXISTS" || echo "NO_STATE_FILE"

If NO_STATE_FILE: Clean up stale pointer and report:

rm -f .shipspec/active-loop.local.json

"No active task loop (stale pointer cleaned up). Run /implement-task <feature> <task-id> to start a task." Stop here.

If found: Parse the JSON state file to extract:

jq -r '.feature // empty' [state_path]
jq -r '.task_id // empty' [state_path]
jq -r '.iteration // 0' [state_path]
jq -r '.max_iterations // 5' [state_path]

• feature: The feature directory name
• task_id: The task being implemented
• iteration: Current attempt number
• max_iterations: Maximum allowed attempts

Store the state_path for cleanup later.

Step 2: Load Task Prompt

The task prompt is stored in TASKS.json, not in the state file.

Read the prompt from TASKS.json:

jq -r --arg id "[task_id]" '.tasks[$id].prompt // empty' .shipspec/planning/[feature]/TASKS.json

Step 3: Run Verification