handofflisted

# Handoff Create a handoff packet: a factual state snapshot plus an executable continuation plan. The packet is for a future agent with fresh context, so it must carry enough ground truth to resume without guessing. ## Workflow 1. **Fix the handoff target.** Infer whether the recipient is the same agent later, another coding agent, a reviewer, QA, or a human. If the user supplied arguments, treat them as the next session focus. Ask one question only when the recipient or purpose changes what must be captured. Done when the packet has a clear recipient, focus, and success condition. 2. **Inventory the current state.** Gather only durable facts: - Original goal and latest user request. - Current repository, branch, environment, and relevant paths. - Files created, edited, or intentionally left untouched. - Commands run, tests run, outputs observed, and commands still running. - Decisions made, options rejected, and why. - Known blockers, risks, assumptions, secrets, credentials, and external dependencies. Prefer artifact references over pasted bulk content. Use paths, URLs, issue IDs, commit hashes, command names, and short evidence quotes. If a command such as `git status` hangs or fails, record that exact fact instead of inventing state. Done when every active thread of work has either a current status, a next action, or an explicit "unknown". 3. **Protect sensitive material.** Redact credentials, tokens, passwords, private personal