Sprint execution — thin wrapper over /claim-tasks. Checks for existing claims and delegates to the merge-queue execution pipeline.
Thin wrapper over /claim-tasks that checks for existing claims and delegates.
/sprint execute (default)Check for existing claims:
scripts/work-queue.sh claimed-by-me
If this worktree has claimed tasks: Check if a handoff file exists at
/tmp/claim-tasks-<worktree>.json (where <worktree> is from
scripts/work-queue.sh output or the worktree directory name).
pending:
Resume Phase 2 of /claim-tasks — invoke the Skill tool with
/claim-tasks execute-pending (the claim-tasks skill will detect
the existing handoff file and skip Phase 1)./claim-tasks with the number of already-
claimed tasks. Phase 1 will detect the existing claims via
and proceed to execution.ALREADY_OWNEDIf no claims exist: Invoke /claim-tasks 1 to claim one task and
execute it.
/sprint planShow what would be claimed without executing:
Load the unified task board:
.venv/bin/python scripts/task-board.py
Use --clusters to see file-overlap groupings.
Use --available-only to show only claimable tasks.
Present the top candidates with priority, files, and review status.
Ask the user to confirm, then invoke /claim-tasks with the selected
count or task names.
/sprint statusEquivalent to /claim-tasks status. Shows this worktree's claims.
scripts/work-queue.sh claimed-by-me
If a handoff file exists at /tmp/claim-tasks-<worktree>.json, also show
the current phase and per-task status from the file.