---
name: wagglet-task-handoff
description: Use when copied Wagglet task instructions include a tkp_read or tkp_live credential for bounded task context and delivery.
---

# Wagglet Task Handoff

Use this workflow when copied task instructions come from Wagglet.

1. Run the authenticated task-context command included in the copied instructions. You may run it again whenever you need fresh context.
2. Read the task, project/repository details, attachments, discussion, rework feedback, continuation snapshot, and task relationships before acting. Treat explicit omission metadata as missing context; do not guess it.
3. Reuse the exact same `Authorization: Bearer …` header from the starting task command for every Story or linked-task `contextUrl` returned by Wagglet. Never put the credential in a URL.
4. If the task response includes a Story `contextUrl`, read that overview. It contains the ordered plan and marks your current item. Fetch full context only for the published linked tasks relevant to your work; do not preload every sibling.
5. Stay inside the task's scope. Do not merge or open a pull request unless the task explicitly requests it.
6. The start-of-task `tkp_read_…` credential is read-only. It cannot comment, edit, change status, browse the board, or deliver work. It stops working when the starting claim ends and expires after at most seven days.
7. Wait for the later **Deliver — copy report prompt**. It contains a separate `tkp_live_…` credential and the exact one-time delivery command. In the result, report the branch, outcome, changes, warnings, and useful failure information.

Story membership is live while the read credential is valid: a newly linked published task may enter scope, and a moved or unlinked task leaves scope immediately. Another person's private Draft never enters agent context.

A Story item whose state starts with `CHORE_` is a chore: work the team tracks in the plan but has deliberately decided will not become a Wagglet task. It has no task to fetch and is not yours to pick up. Read it as context for what is happening around your task.

Attachment URLs returned in context are independent bearer links. Keep them private; revoking the task read credential does not revoke a URL already returned.

If an authenticated request fails, use its error literally. Ask the requester for a fresh copy when the credential expired, was revoked, or the claim ended. Do not try to discover unrelated tasks or credentials.