worker-handover

Posts structured context handovers to GitHub issue comments when workers reach turn limits.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill worker-handover-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: worker-handover
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/worker-handover
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill worker-handover-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI worker approaches its 100-turn limit mid-task, all accumulated context risks being lost. This Skill defines a structured handover format posted to GitHub issue comments so a replacement worker can resume the task with full context. ## Core Features & Use Cases - Structured Handover Format: Provides a Markdown template with metadata, branch status, test results, decisions, gotchas, and recommended next steps, delimited by HANDOVER:START/END markers. - GitHub-Based State Storage: Stores handover context in issue comments rather than local files, so it survives worker crashes. - Handover Reception Workflow: Guides replacement workers through reading the latest handover via the GitHub API, verifying branch and test state, and posting an acknowledgment. - Use Case: A worker at turn 94 of 100 posts a handover comment to issue #123 summarizing commits, failing tests, and next steps; the orchestrator spawns a replacement worker that reads the comment and continues seamlessly. ## Quick Start Create a handover for issue 123 documenting my current branch state, test results, and recommended next steps, then post it as an issue comment.

Frequently Asked Questions about worker-handover

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

FAQPage Schema
How do I hand over work to a replacement AI worker?▼

Post a structured handover comment to the GitHub issue using the HANDOVER:START/END markers, including branch status, test results, decisions, and next steps. Commit all uncommitted work before exiting so the replacement worker can verify state.

When should a worker create a handover?▼

Evaluate handover need at 85 turns, begin preparation at 90 turns, and complete the handover by 95 turns. The worker exits automatically at 100 turns, so the handover must be posted before that point.

Where is handover context stored?▼

Handover context is stored in GitHub issue comments, never in local files. This ensures the handover survives worker crashes and is accessible to any replacement worker via the GitHub API.

How does a replacement worker read a handover from GitHub?▼

Use the gh api command to fetch issue comments and filter for the one containing the HANDOVER:START marker, taking the last match. Then verify the branch and test state match the handover before continuing work.

What makes a handover too vague to be useful?▼

Handovers fail when they lack specifics, such as saying "did some stuff" or "fix the tests" without explaining why tests fail. A good handover includes commit references, failure details, decision rationale, gotchas, and tested commands.