handoff

Parse YAML task handoff files and manage pending, in-progress, and completed tasks.

2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/dd-xiaozhi/dev-agent-flow --skill handoff-dd-xiaozhi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/dd-xiaozhi/dev-agent-flow/tree/main/.claude/skills/handoff
Command: npx skills add https://github.com/dd-xiaozhi/dev-agent-flow --skill handoff-dd-xiaozhi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the communication gap between upstream roles (PM/SA) and execution teams by providing a structured, persistent channel for task handovers, eliminating the need for manual status tracking and verbal relay.

Core Features & Use Cases

  • Structured Task Consumption: Automatically scans and prioritizes pending tasks from a dedicated directory.
  • Lifecycle Management: Tracks tasks through pending, in-progress, and completed states with audit trails.
  • Use Case: A Product Manager drops a new feature requirement file into the handoff directory, and the developer uses this skill to pull, prioritize, and execute the task while maintaining a clear record of progress and completion.

Quick Start

Run the handoff skill to scan the pending directory and select a high-priority task to begin execution.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I automate cross-role task handovers between product management and development?

Automating cross-role task handovers requires a structured, persistent channel for task transitions to eliminate manual status tracking. The handoff skill consumes YAML-defined task metadata from project directories to seamlessly prioritize, track, and archive work items between product management and development roles.

How does YAML task metadata parsing manage the task lifecycle?

YAML task metadata parsing manages the task lifecycle by scanning dedicated directories to track items through pending, in-progress, and completed states. This standardized process maintains cross-session state persistence and audit trails without requiring manual status updates.

What directory structure is needed for tracking pending and completed tasks?

Tracking pending and completed tasks requires a consistent directory structure for pending, in-progress, and completed items. This standardized folder organization ensures cross-session state persistence so the handoff skill can automatically scan, prioritize, and archive work items.

Does task handoff work without manual status tracking and verbal relay?

Yes, task handoff works without manual status tracking by providing a structured, persistent channel for task transitions. It consumes YAML-defined task files from project directories, automatically bridging the communication gap between upstream roles and execution teams.

Can I use this approach for cross-session state persistence in task management?

You can achieve cross-session state persistence in task management by relying on a consistent directory structure for pending, in-progress, and completed tasks. The handoff skill parses YAML-defined task metadata within these directories to maintain continuous work item tracking.