apm-7-handoff-worker

Creates Handoff Logs and handoff prompts to transfer Worker context between APM instances.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ZK-Theory/TDL --skill apm-7-handoff-worker-zk-theory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apm-7-handoff-worker
Source: https://github.com/ZK-Theory/TDL/tree/main/.agents/skills/apm-7-handoff-worker
Command: npx skills add https://github.com/ZK-Theory/TDL --skill apm-7-handoff-worker-zk-theory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an APM Worker agent approaches its context window limit, its working context would be lost. This Skill preserves continuity by generating a structured Handoff Log and a handoff prompt so an incoming Worker instance can reconstruct context and resume work. ## Core Features & Use Cases - Handoff Log Creation: Captures past actions, working context, patterns, and technical notes in .apm/memory/handoffs/<agent>/ with a defined YAML frontmatter schema. - Handoff Prompt Generation: Writes a present-tense continuation prompt to the Handoff Bus at .apm/bus/<agent-slug>/handoff.md, covering mid-Task, mid-batch, and between-Tasks scenarios. - Use Case: A Worker agent mid-Task hits its context limit. Run this Skill to produce both artifacts, then start a new chat and run /apm-3-initiate-worker so the incoming instance auto-detects the handoff and resumes from the exact step. ## Quick Start Initiate the Worker Handoff procedure to create the Handoff Log and handoff prompt for the incoming Worker instance.

Frequently Asked Questions about apm-7-handoff-worker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off work between APM Worker instances?

Run the handoff command when the Worker nears its context limit. It creates a Handoff Log in `.apm/memory/handoffs/<agent>/` and a handoff prompt on the Handoff Bus, then you start a new chat and run `/apm-3-initiate-worker` so the incoming instance auto-detects the handoff.

What is the difference between a Handoff Log and a handoff prompt?

The Handoff Log records past actions, working context, and technical notes from the current instance in past tense. The handoff prompt describes current state and continuation guidance in present tense, telling the incoming Worker what to read and do next.

How does the incoming Worker rebuild context after a handoff?

The incoming Worker reads the Handoff Log plus the current Stage Task Logs, not the Handoff Log alone. It must not load previous-Stage logs, since the Manager supplies cross-Stage dependency context through Task Prompts.

What happens if a handoff occurs mid-Task or mid-batch?

For mid-Task, the prompt directs the incoming Worker to read the intact Task from the Task Bus and resume from the specified step. For mid-batch, it describes each Task's state so the incoming Worker continues the batch from where work stopped.

Why must the incoming Worker indicate handoff status in its first Task Report?

The status indication triggers the Manager's Handoff detection, which affects dependency context classification for future Task assignments. It must state the instance number, list the Task Log files loaded, and note when previous-Stage logs were not loaded.