task-handoff-writing
Write high-signal handoffs (`HANDOFF.md` or `docs/handoffs/<slug>.md`) with concrete validation evidence and actionable next steps.
When & Why to Use This Skill
The Task Handoff Writing skill for Claude automates the creation of high-signal technical documentation to ensure seamless project continuity. By capturing repository snapshots, validation evidence, and actionable next steps, it helps users and AI agents overcome context limits and maintain momentum across work sessions or team transitions.
Use Cases
- Case 1: AI Context Management - Automatically generate a structured handoff when an AI agent reaches its context window limit, allowing a fresh session to resume work with full technical state and history.
- Case 2: Technical Team Handoffs - Create comprehensive HANDOFF.md files for teammates that include current git status, recent logs, and verification results to ensure a smooth pickup of 'parked' tasks.
- Case 3: Task Suspension and Resumption - Document the precise state of a complex feature development before switching priorities, ensuring that 'actionable next steps' and exact commands are ready for future use.
- Case 4: Quality Gate Documentation - Integrate quality gate status and validation evidence into project updates to provide concrete proof of progress and maintain high standards of transparency.
| name | task-handoff-writing |
|---|---|
| description | Write 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
- Capture repo snapshot:
git status -sbandgit log -n 5 --oneline - Capture quality gate status:
./verify.sh --ui=false - Write a handoff with: Problem Statement → Current Snapshot → Next Steps (with exact commands) → Risks → References.
Canonical repo doc
Read docs/skills/handoff-writing.md.