pickup

To resume a previous agent session, the Skill locates and reads HANDOFF.md in the working directory or git project root, summarizing goals and next steps. It verifies the active branch, uncommitted changes, and recent commits to ensure repository state matches the handoff before proceeding.

The best way to orient a new agent is using a HANDOFF.md document. The Skill reads this file to capture context, runs git checks to confirm branch and uncommitted changes match the recorded state, and presents a concise summary for user confirmation before doing any work.

No, the handoff resume process does not automatically delete HANDOFF.md. The Skill only removes the handoff document after the user provides explicit confirmation, ensuring stale instructions do not linger but preventing accidental loss of context.

Yes, you can use a handoff document to verify uncommitted changes. The Skill runs git checks to confirm the active branch, uncommitted changes, and recent commits align with the handoff file before summarizing the plan and waiting for confirmation.

If HANDOFF.md is missing from the working directory, the Skill searches for it in the git project root. It reads the first HANDOFF.md file found in either location to capture the prior session's goals and next steps for resuming work.

You should not use a handoff document for session resumption if your repository state has significantly diverged from the recorded branch and uncommitted changes. The Skill verifies git state against the handoff, and mismatches may prevent safe continuation of the prior work.