Agent Skills: handoff

Compact the current conversation into a handoff document for another agent to pick up.

UncategorizedID: zenobi-us/dotfiles/handoff

Install this agent skill to your local

pnpm dlx add-skill https://github.com/zenobi-us/dotfiles/tree/HEAD/devtools/files/agent/bundles/matt-pocock/skills/handoff

Skill Files

Browse the full folder contents for handoff.

Download Skill

Loading file tree…

devtools/files/agent/bundles/matt-pocock/skills/handoff/SKILL.md

Skill Metadata

Name
handoff
Description
Compact the current conversation into a handoff document for another agent to pick up.

Language

All agent-authored prose MUST follow ASD-STE100 Simplified Technical English. Apply it to questions, explanations, recommendations, issue text, reports, handoffs, and procedures.

  • Use short, complete sentences and active voice.
  • Use one term for one meaning.
  • Put conditions before commands.
  • Use imperative sentences for procedures.
  • Keep code, identifiers, commands, quoted text, product names, and exact domain terms unchanged.
  • Use the simple-english skill for the full rule set.

Local repository rules

Before reading or writing workflow or domain artifacts:

  1. Follow ALIGNMENT-ROOT.md.
  2. Resolve alignment paths against ALIGNMENT_ROOT.
  3. Keep source code and ordinary project files relative to repository-root.
  4. Do not silently mix alignment roots.
  5. All agent-authored prose MUST follow ASD-STE100 Simplified Technical English.

Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.

Include a "suggested skills" section in the document, naming which skills the next agent should call the Skill tool for.

Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.

Redact any sensitive information, such as API keys, passwords, or personally identifiable information.

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.