skills.rest
dusktreader
dusktreaderCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

handoff-workflow

Generate structured handoff documents as .pending.md files for AI agent transfers.

Updated Feb 3, 2026
Search Tags:#workflow#template#documentation#handoff#session#OpenCode
One-click install
npx skills add https://github.com/dusktreader/site-nine --skill handoff-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff-workflow
Source: https://github.com/dusktreader/site-nine/tree/main/.opencode/skills/handoff-workflow
Command: npx skills add https://github.com/dusktreader/site-nine --skill handoff-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handoff workflow solves the challenge of preserving context when transferring tasks between agents by generating a structured, shareable handoff document that captures state, decisions, and next steps.

Core Features & Use Cases

  • Create a standardized handoff document using the handoff template from the project.
  • Save the document as a .pending.md file in the designated .opencode/work/sessions/handoffs/ folder for awaiting acceptance.
  • Update the originating session with handoff metadata and provide clear recipient instructions.
  • Suitable for delegations between roles (Administrator to Engineer, Engineer to Tester, Inspector to Documentarian, etc.) to maintain continuity.

Quick Start

  1. From your current session, identify context, state, and next steps.
  2. Use the template at .opencode/templates/handoff-template.md to generate the handoff document.
  3. Save it to .opencode/work/sessions/handoffs/YYYY-MM-DD.HH:MM:SS.from-role-name.to-role.pending.md.
  4. Update your session file with a Handoff entry and summary.
  5. Inform the next agent to run /summon and review the pending handoff.

Frequently Asked Questions about handoff-workflow

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

FAQPage Schema
How do I preserve context when handing off work between AI agents?▼

Handoff workflow automatically generates a structured handoff document that captures session state, decisions, and next steps. It saves the document as a .pending.md file in your .opencode/work/sessions/handoffs/ folder, enabling the recipient agent to resume work with full context intact.

What should be included in a handoff document for agent transitions?▼

A handoff document should include current context, session state, completed decisions, and clearly defined next steps. The handoff-workflow skill uses a standardized template from .opencode/templates/handoff-template.md to structure this information consistently across role-to-role delegations.

How do I transfer a task from one agent role to another in a multi-agent workflow?▼

Identify your current context and next steps, generate a handoff document using the standardized template, save it with the naming format YYYY-MM-DD.HH:MM:SS.from-role-name.to-role.pending.md, update your session file with handoff metadata, then notify the recipient to run /summon to accept the pending handoff.

Can handoff documents work across different agent roles and responsibilities?▼

Yes, handoff workflow supports delegations between any roles—Administrator to Engineer, Engineer to Tester, Inspector to Documentarian, and beyond. The standardized template and metadata structure maintain continuity regardless of the role pairing or workflow complexity.

What happens to session state when I create a handoff?▼

Your originating session is updated with handoff metadata documenting the transfer. The recipient receives a pending handoff document that preserves all context, decisions, and state information, allowing them to continue seamlessly without loss of knowledge or progress.

Where should pending handoff documents be stored?▼

Pending handoff documents are saved in the .opencode/work/sessions/handoffs/ directory with a timestamp and role-based filename. This standardized location allows recipient agents to discover and accept handoffs through the /summon command.

Related Skills

Explore More Software Engineering Skills→
arielZusmanarielZusman

handoff-summary

Generate structured handoff summaries with progress, decisions, and context sections.

Community
Intermediate
pagerguildpagerguild

context-loader

Load tiered project context for cross-session and cross-agent workflows.

Official
Advanced
jinwoonghongjinwoonghong

moai-foundation-context

Manage token budgets and persist session state for multi-agent workflows.

Community
Advanced
latestaiagentslatestaiagents
5

agent-handoff-protocols

Define direct, queued, and brokered handoff protocols for multi-agent workflows.

Official
Advanced