handoff

Update CURRENT, NEXT, RISKS, and TODO state and sync documentation during team handoffs.

3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/dadwadw233/team-collab-skills --skill handoff-dadwadw233
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/dadwadw233/team-collab-skills/tree/main/skills/handoff
Command: npx skills add https://github.com/dadwadw233/team-collab-skills --skill handoff-dadwadw233

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The current handoff flow often lacks a standardized transition between sessions, causing ownership ambiguity, state drift, and documentation misalignment. This Skill provides a centralized handoff flow that updates project state and keeps all relevant docs in sync.

Core Features & Use Cases

  • Update and align the state quartet (CURRENT, NEXT, RISKS, TODO) at handoff milestones.
  • Sync and propagate documentation changes across the project to avoid handoff gaps.
  • Read and enforce the full team-collab protocol, ensuring governance even when invoked indirectly.

Quick Start

Say '$handoff <topic>' to initiate a structured handoff and trigger the docs sync workflow.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I coordinate a team handoff and keep documentation synced?

To coordinate a team handoff and keep documentation synced, initiate a structured handoff to update the CURRENT, NEXT, RISKS, and TODO state quartet while triggering the docs sync workflow.

What is the best way to manage session state drift during project transitions?

Managing session state drift during project transitions requires a standardized handoff flow that updates project state quartets and propagates documentation changes to avoid ownership ambiguity and gaps.

How does git sync conflict handling work during a live session handoff?

Git sync conflict handling during a live session handoff works by enforcing end-to-end protocol ownership with safety guards, delegating to the installed team-collab-protocol for full behavior and conflict resolution.

Do I need a team-collab protocol installed to execute handoff requests?

Yes, you need a team-collab protocol installed or installable to execute handoff requests, as the skill reads and enforces the full protocol to ensure governance even when invoked indirectly.

Can I update project TODO and RISKS documentation automatically at session completion?

Yes, you can update project TODO and RISKS documentation automatically at session completion by triggering the centralized handoff flow, which aligns the state quartet and syncs relevant docs across the project.

Why does handoff documentation get misaligned without a standardized protocol?

Handoff documentation gets misaligned without a standardized protocol because the flow lacks a centralized transition between live sessions, causing ownership ambiguity, state drift, and documentation misalignment.