handoff

Prepare a concise, reliable handoff so another person or agent can continue work. Use when context may be lost, a task changes owners, or a session is ending.

SKILL.md

GitHub

Handoff

Create a continuation note that makes the next action obvious without repeating the entire conversation.

Include:

  • Goal and current status: what is being built or investigated and what is actually complete.
  • Decisions: settled choices and the reasons that matter.
  • Files and state: key paths, branch/worktree, commands run, and current working-tree condition.
  • Evidence: test/check results, logs or artifacts, and exact failures.
  • Open work: ordered next steps, blockers, risks, and unanswered questions.
  • Constraints: user preferences, security boundaries, external permissions, and non-goals.

Distinguish facts from hypotheses. Do not claim tests passed unless observed. Never include credentials, private tokens, or unnecessary personal information. Prefer stable file references over long copied code. Keep the handoff short enough to scan but complete enough to resume.