task-handoff-writing

Write high-signal handoffs (`HANDOFF.md` or `docs/handoffs/<slug>.md`) with concrete validation evidence and actionable next steps.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill automates the creation of high-signal handoff documentation (HANDOFF.md) to ensure seamless task transitions and prevent context loss. It solves the critical problem of 'work fragmentation' by capturing repository snapshots, validation evidence, and actionable next steps, making it indispensable for developers and AI agents hitting context limits or transferring tasks to teammates.

Use Cases

  • Scenario 1: Managing AI context limits by 'parking' current progress into a structured document before starting a fresh session to maintain continuity.
  • Scenario 2: Facilitating smooth developer handovers by providing a clear 'Current Snapshot' and exact commands for the next person to pick up the work.
  • Scenario 3: Documenting technical debt or paused features with concrete validation evidence (via verify.sh) and risk assessments for future resumption.
  • Scenario 4: Preparing for code reviews by summarizing the problem statement and providing a 'Fast Path' for reviewers to verify the implementation.
nametask-handoff-writing
descriptionWrite high-signal handoffs (`HANDOFF.md` or `docs/handoffs/<slug>.md`) with concrete validation evidence and actionable next steps.

Handoff Writing

When to use

Use this when the task mentions:

  • “handoff”, “context limit”, “I can’t finish”, “park this work”
  • preparing for review / teammate pickup

Fast path

  1. Capture repo snapshot: git status -sb and git log -n 5 --oneline
  2. Capture quality gate status: ./verify.sh --ui=false
  3. Write a handoff with: Problem Statement → Current Snapshot → Next Steps (with exact commands) → Risks → References.

Canonical repo doc

Read docs/skills/handoff-writing.md.