handoff

Generate a structured HANDOFF.md at the project root with goal, progress, and next steps.

9.6k|760|Updated Nov 28, 2025
One-click install
npx skills add https://github.com/ykdojo/claude-code-tips --skill handoff-ykdojo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/ykdojo/claude-code-tips/tree/main/skills/handoff
Command: npx skills add https://github.com/ykdojo/claude-code-tips --skill handoff-ykdojo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write a concise, shareable handoff document that captures context for the next agent and ensures continuity.

Core Features & Use Cases

  • Structured Goal, Current Progress, What Worked, What Didn't Work, and Next Steps sections.
  • Suitable for project handoffs, onboarding new teammates, and cross-team transitions.
  • Example: Generate HANDOFF.md at the project root summarizing goals, progress, decisions, and next actions.

Quick Start

Use this skill to create a HANDOFF.md in the project root that contains sections for Goal, Current Progress, What Worked, What Didn't Work, and Next Steps.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I create a handoff document for project transitions?

To create project transition documentation, this skill generates a structured HANDOFF.md at your project root, capturing the goal, current progress, lessons learned, and clear next steps to preserve context for the next agent or teammate.

What should be included in knowledge transfer documentation for onboarding new teammates?

Knowledge transfer documentation for onboarding new teammates should include the project goal, current progress, what worked, what didn't work, and clear next steps. This skill enforces this structured format into a concise HANDOFF.md file.

Can I generate a HANDOFF.md file automatically at my project root?

Yes, you can generate a HANDOFF.md file automatically at your project root. This skill enforces a structured documentation format to summarize goals, progress, decisions, and next actions for seamless cross-team project transitions.

What is the best way to preserve project context for the next agent?

The best way to preserve project context for the next agent is creating a concise, shareable handoff document. This skill generates a structured HANDOFF.md capturing goals, progress, lessons learned, and next steps to ensure project continuity.

Does this handoff documentation skill work without any dependencies?

Yes, this handoff documentation skill works without any dependencies. It directly enforces a structured format and creates a HANDOFF.md file at the project root to capture project context, decisions, and next steps.