tda-handoff

Generates structured session handoff documents that preserve task state across agent runtimes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a long session ends, an agent runtime switches, or context is about to be lost, critical decisions and task state can disappear. This Skill produces a compact handoff document that references artifacts by path so another agent or future session can continue without re-deriving prior work. ## Core Features & Use Cases - Structured Handoff Template: Produces a standardized Markdown packet covering capability status, completed production path, exact remaining gap, next action, commands run, decisions, risks, and a do-not-do list. - Dispatch Safety for Autonomous Agents: Adds hard stops, blocking user-decision gates, and provenance rules when the handoff will be consumed by an autonomous successor rather than a person. - Collision-Safe Naming and Path Rules: Mints ULID-prefixed filenames via a system script and routes standalone handoffs to authorized neutral paths instead of APM state. - Use Case: Before ending a research coding session, generate a handoff that records the capability state as RUNNABLE, lists exact re-runnable commands, and names the next production action so a fresh agent resumes immediately. ## Quick Start Ask the agent to create a TDA handoff for the current session before switching runtimes or pausing the task.

Frequently Asked Questions about tda-handoff

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

FAQPage Schema
How do I hand off a coding session to another AI agent?

Create a handoff document that records capability status, the completed production path, the exact remaining gap, and the next production action. Reference files and commands by path rather than copying content, and add hard stops if an autonomous agent will consume it.

What should a session handoff document include?

Include the active project, capability state, completed production path, exact remaining functional gap, next action, commands run, contracts and validation status, decisions with references, open risks, and a tailored do-not-do list.

When should I not write a session handoff?

Skip the handoff when the session was trivial or its outcome is already fully captured in a commit, plan, or vault entry. APM Manager/Worker workflows use their own numbered handoff skills and Memory Bank instead.

How do I make a handoff safe for an autonomous agent?

Bound scope with explicit hard stops, restate user-decision gates as blocking rather than advisory, and repeat result provenance rules. State what remains forbidden even after a precondition clears, since autonomous readers interpret open-ended handoffs maximally.

Why do handoff file links break on Windows?

Backslashes act as Markdown escape characters, so native Windows paths in links can render with separators consumed and produce broken targets. Use forward slashes in clickable links and show native-spelled paths separately as inline code.