worker-handoff

Defines delegation conventions and standardized handoff report templates for sub-agent task dispatch.

2|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/ShineBreaker/Guix-configs --skill worker-handoff-shinebreaker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: worker-handoff
Source: https://github.com/ShineBreaker/Guix-configs/tree/main/dotfiles/mutable/agents/hermes/.local/share/hermes/skills/autonomous-ai-agents/worker-handoff
Command: npx skills add https://github.com/ShineBreaker/Guix-configs --skill worker-handoff-shinebreaker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a main agent session splits large tasks across parallel sub-agents, results come back in inconsistent formats, making it hard to judge trustworthiness, retry failures, or chain follow-up work. This Skill standardizes how tasks are delegated via delegate_task and how workers report back. ## Core Features & Use Cases - Delegation Patterns: Rules for when to use workers, parallel vs. serial dispatch, and how to embed worker behavior norms into sub-agent context. - Standardized Handoff Template: A mandatory Markdown report format covering status, branch, measurements, verification level, changed files, decisions, risks, and suggested follow-ups. - Verification & Recovery: A four-tier verification scale (live-ui-verified to not-verified) plus a failure-mode retry policy (cap-hit, network-drop, tool-error) with a two-retry budget. - Use Case: You have a large refactor spanning multiple modules. Load this Skill, split the work into non-overlapping subtasks, dispatch them in parallel with delegate_task, then consume each handoff report to decide what to trust, retry, or send to code review. ## Quick Start Load the worker-handoff skill and split my current refactoring task into parallel sub-agents that each return a standardized handoff report.

Frequently Asked Questions about worker-handoff

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

FAQPage Schema
How do I delegate subtasks to parallel AI agents?▼

Split the work into independent, non-overlapping subtasks and dispatch them with delegate_task using a tasks array. Embed worker behavior norms and the handoff template in each sub-agent's context so results return in a consistent format.

What should a sub-agent handoff report include?▼

A handoff report should include status (success, partial, blocked), branch name, summary of changes, quantitative measurements, a verification level, a table of changed files, key decisions, validation results, risks, and suggested follow-up tasks.

When should I use sub-agents instead of doing the work directly?▼

Use workers for cross-file or multi-module implementations, independently verifiable bug fixes with regression tests, mechanical execution of a ready plan, and large refactors. Avoid them for small single-file edits where delegation overhead exceeds the benefit.

How do I handle a failed or blocked sub-agent task?▼

Match the failure mode to a strategy: narrow the scope for cap-hit or OOM, retry as-is for network drops, switch models for tool errors, and retry once for unknown failures. Abandon and re-plan after two failed retries on the same task.

What verification level makes a sub-agent result trustworthy?▼

Live UI verification is trusted as shipped, and unit-test verification is acceptable for non-UI bugs. Results marked type-check-only or not-verified are weak and must be sent to a code reviewer before acceptance.