sdd-handover

Generate a structured handover.md document from session decisions and issues.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/sync-dev-org/sync-sdd --skill sdd-handover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-handover
Source: https://github.com/sync-dev-org/sync-sdd/tree/main/framework/claude/skills/sdd-handover
Command: npx skills add https://github.com/sync-dev-org/sync-sdd --skill sdd-handover

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that critical information, decisions, and context from a development session are preserved and clearly communicated, enabling smooth transitions between AI agents or human developers across different sessions.

Core Features & Use Cases

  • Automated Session Archiving: Consolidates and archives decisions, issues, and knowledge from the current session.
  • Structured Handover Document Generation: Creates a handover.md file detailing session accomplishments, immediate next steps, and resume instructions.
  • Work Commit Proposal: Suggests and executes commits for work completed during the session before generating the handover.
  • Use Case: At the end of a complex feature development session, use this Skill to generate a handover document that clearly outlines what was built, any open issues, and the exact command the next developer should run to pick up where you left off.

Quick Start

Use the sdd-handover skill to generate a polished session handover document.

Frequently Asked Questions about sdd-handover

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

FAQPage Schema
How do I generate a session handover document for cross-session continuity?

To generate a session handover document, the Skill consolidates decisions, issues, and knowledge from your session, archives stale entries, and produces a structured handover.md file through user dialogue.

What is the best way to archive stale session data before handing off to another developer?

The best way to archive stale session data is to use an automated session archiving process that consolidates decisions, issues, and knowledge, clearing outdated entries before generating a handover document.

How does a session handover document preserve development context for AI agents?

A session handover document preserves development context for AI agents by detailing session accomplishments, immediate next steps, and exact resume instructions in a structured markdown file.

Can I propose work commits automatically before generating a knowledge management handover file?

Yes, you can propose work commits automatically; the Skill suggests and executes commits for work completed during the session before it generates the final handover document.

Does the handover generation process support manual polish mode for documentation?

Yes, the handover generation process supports manual polish mode, allowing you to refine the consolidated session data and documentation before finalizing the structured handover.md output.

When do I need to generate a handover document during software development?

You need to generate a handover document at the end of a complex feature development session to clearly communicate critical information, decisions, and open issues for smooth transitions between developers.