yak-wrap

To generate a session worklog, invoke a session wrap tool to harvest completed tasks, collect their context and comments, and append a summary to the session comments file. This enables tidy handoffs and prepares the remaining work for the next cycle.

Pruning completed tasks involves harvesting their final state and stories, then removing them from the active task map. This reorganizes the remaining work items, ensuring the next session starts with a clean and updated view of pending tasks.

You need to wrap a multi-agent work session when concluding a collaborative work cycle. Wrapping harvests completed work, generates a worklog, prunes finished items, and synchronizes the updated state to prepare the environment for the next operational cycle.

Session wrapping supports optional synchronization to propagate updated state to remote storage. This ensures that harvested worklogs and pruned task maps are consistently backed up across environments for seamless multi-agent handoffs.

Harvesting completed work items involves extracting their context, shaver-messages, comments, and supervision details. This collected data forms the basis of the session worklog, capturing the full narrative of what was achieved during the work cycle.

Yes, using a deterministic session wrap workflow automates end-of-session handoffs by harvesting done tasks, generating worklogs, and pruning the map. This removes the need for manual cleanup and ensures consistent preparation for the next cycle.