handoff

Generate a continue.md handoff package and update STATE.md summaries.

12|1|Updated May 29, 2026

Search Tags:#workflow #handoff #state-management #summaries #slices #continue.md

Ready to run

npx skills add https://github.com/qdzsh/gsd-revamp --skill handoff-qdzsh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/qdzsh/gsd-revamp/tree/main/src/resources/skills/handoff
Command: npx skills add https://github.com/qdzsh/gsd-revamp --skill handoff-qdzsh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handoff prevents context loss between sessions by producing a concise handoff package that lets the next agent resume work quickly.

Core Features & Use Cases

Write a minimal continue.md in the active slice to capture the last actions, evidence, and the next concrete step.
Update STATE.md and the slice-level and project-wide summary artifacts to maintain a coherent project history.
Provide clear open threads for the future work and avoid leaking secrets or stale context.

Quick Start

Trigger a handoff to generate a continue.md and refresh project summaries for the next agent.

Frequently Asked Questions about handoff

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

FAQPage Schema

How do I prevent context loss when handing off work between agents across sessions?▼

To prevent cross-session context loss, you can generate a concise handoff package that creates a continue.md file capturing last actions, evidence, and the next concrete step for the next agent.

What is the best way to create a continue.md file for task pauses or end-of-session reviews?▼

The best way to create a continue.md during task pauses is to trigger a handoff, which writes a minimal file in the active slice to capture the last actions and the next concrete step.

How does state management work when updating STATE.md and project summary artifacts for future work?▼

State management during a handoff works by updating STATE.md and slice-level summary artifacts to maintain a coherent project history and record open threads for future work.

Does the handoff process avoid leaking secrets or stale context when resuming work between agents?▼

Yes, the handoff process provides clear open threads for future work while explicitly avoiding the leakage of secrets or stale context when passing tasks between agents.

When do I need to generate a handoff package for cross-session workflows?▼

You need to generate a handoff package during task pauses, end-of-session reviews, or when handing off work between agents to ensure quick re-entry into the active slice.

Can I use this workflow to maintain a coherent project history across multiple agents?▼

Yes, you can use this workflow to maintain a coherent project history by updating STATE.md and project-wide summary artifacts, allowing the next agent to resume work quickly.